Cannot import swagger file with ref in parameters

[IamIpanda]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.4.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Import following swagger file for custom tools:

---
openapi: 3.0.3
info:
  title: Example 
  version: 1.0.0
servers:
- url: https://dify.ai
  description: Example server
paths: 
  "/auth":
    get:
      summary: performs authentication services
      operationId: auth_get
      parameters:
      - "$ref": "#/components/parameters/param1"
      responses:
        '200':
          description: Authorization Response
components:
  parameters:
    param1:
      name: response_type
      in: query
      schema:
        type: string
        enum:
        - enum1 
        - enum2
      required: true

This is a legal swagger file.

✔️ Expected Behavior

Import success

❌ Actual Behavior

can't find the parameter name because ref is not resolved.

[dosubot]

Based on the codebase, Dify’s Swagger/OpenAPI import logic is designed to resolve $ref references in request bodies, but it appears that references in the parameters section (like "$ref": "#/components/parameters/param1") may not be fully dereferenced during import. The relevant parser (ApiBasedToolSchemaParser in parser.py) processes parameters and converts them into tool parameters, but the explicit logic for resolving $ref in parameters is not as robust as for request bodies or schemas. This could explain why your referenced parameter is not being recognized during import, resulting in the error you observed "parser.py".

There are no existing issues or documentation entries addressing this specific problem.

To work around this, try inlining the parameter definition directly in the parameters array instead of using $ref. If you need to use $ref for maintainability, you may need to adjust the import logic in Dify to explicitly resolve parameter references, similar to how it handles $ref in request bodies.

If you continue to encounter issues, providing logs or more details about the import process could help pinpoint where the reference resolution is failing.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}